feat: Futurehome TS0601 expose energy consumption #11373
Conversation
src/devices/futurehome.ts
Outdated
| return {}; | ||
| } | ||
|
|
||
| globalStore.putValue(meta.device, "energy_last", scaled); |
There was a problem hiding this comment.
This store resets on every z2m restart (so that means that energy would be lost every time). You can persist it in _meta.device.meta.energy = xx; instead (this is saved to the data/database.db)
There was a problem hiding this comment.
Thanks for the suggestion! I was initially thinking that it does not matter if the status is lost on z2m restart as they are so rare, but it definitely makes sense as persisting the data turned out to be that easy.
FYI, the thermostat is really noisy, and I think it is internally sending stale data once in a while during its transmit bursts. This is what a non-filtered heating period looked on Homeassistant side:
(I patched the filtering into my z2m container at the vertical line)
Expose energy consumption metric, ignoring outdated values which seem to happen often at least in a busier network.
|
Thanks! |
|
Thanks a lot! This is a very welcome and huge improvement – I can now access information on total energy usage per futurehome thermostat via the Zigbee2MQTT device panel. This is awesome! However, when I add a device such as sensor.fh_4_zb_3_meter_elec_e_import in the energy panel, nothing is updated / added. (I waited for a day to be sure.) When I monitor current activity in the Zigbee2MQTT device panel, I see regular updates from other devices (such as my Futurehome provided smart plug and my Futurehome provided Develco HAN sensor), but nothing from the futurehome thermostats. Is this information not available or do I need to do something to access current energy consumption? |
3 participants
Expose energy consumption metric, ignoring outdated values which seem to happen often at least in a busier network.
Fixes feature request Koenkk/zigbee2mqtt#23139